Method for detecting failures of random access procedures

ABSTRACT

A method of performing a random access channel (RACH) procedure between a mobile terminal and a network includes the steps of detecting whether a random access response (RAR) is received from the network within a certain time period, the RAR including information about a random access channel (RACH) preamble transmitted to the network; and if the RAR is not received within the certain time period or if the information about the transmitted RACH preamble included in the RAR does not match the transmitted RACH preamble, performing a first procedure to detect failures in the RACH procedure; and if the RAR is received within the certain time period and if the information about the transmitted RACH preamble included in the RAR matches the transmitted RACH preamble, performing a second procedure to detect failures in the RACH procedure.

CROSS-REFERENCE

This application is a continuation of, and claims the benefit of U.S.application Ser. No. 13/896,189 filed May 16, 2013, which is acontinuation of U.S. application Ser. No. 13/101,565 filed May 5, 2011(now U.S. Pat. No. 8,477,634), which is a continuation of U.S.application Ser. No. 12/457,654, filed Jun. 17, 2009 (now U.S. Pat. No.7,957,298), and claims priority benefit to U.S. Provisional ApplicationNo. 61/073,743, filed Jun. 18, 2008, U.S. Provisional Application No.61/074,998, filed Jun. 23, 2008, and Korean Patent Application No.10-2009-0053407, filed Jun. 16, 2009 (now Korean Patent No. 10-0980919),the contents of each of the above-identified applications is herebyincorporated by reference herein in its entirety.

BACKGROUND

The present invention relates to an apparatus and method for detectingfailures of random access procedures. In the related art, failures ofrandom access procedures were not detected properly. As such, therelated art technologies do not sufficiently address such issues, andthus do not offer appropriate solutions.

SUMMARY

The present inventors recognized at least the above-identified drawbacksof the related art. Based upon such recognition, the various featuresdescribed hereafter have been conceived such that instead of waiting toreport about any problems that occur in the RACH procedure, if a RACHprocedure failure is detected, such failure is reported immediately tothe upper layer (RRC entity), then the MAC entity (sub-layer) performserror correction and the RACH procedure is performed again, whichresults in less delays.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an exemplary network architecture for an E-UMTS (EvolvedUniversal Mobile Telecommunications System).

FIG. 2 shows an exemplary radio interface protocol architecture for thecontrol plane between the mobile terminal (UE) and the network (eNB,MME).

FIG. 3 shows an exemplary radio interface protocol architecture for theuser plane between the mobile terminal (UE) and the network (eNB, SAEGateway).

FIG. 4 shows an exemplary signal flow diagram of a contention basedrandom access procedure between the mobile terminal (UE) and the basestation (eNB).

FIG. 5 shows an exemplary relationship among certain channels (PDCCH andPDSCH) between the base station and mobile terminal.

FIG. 6 shows a signal flow diagram according to an exemplary embodiment.

FIG. 7 shows a flow chart according to an exemplary embodiment.

FIG. 8 shows a flow chart according to another exemplary embodiment.

FIG. 9 shows the structural block diagram of a UE (100) and eNB (200)according to the exemplary embodiments.

DETAILED DESCRIPTION

The inventive concepts and features herein are explained in terms of aLong Term evolution (LTE) system or other so-called 4G communicationsystems, which is an enhancement to current 3GPP technologies. However,such details are not meant to limit the various features describedherein, which are applicable to other types of mobile and/or wirelesscommunication systems and methods.

Hereafter, the term “mobile terminal” will be used to refer to varioustypes of user devices, such as mobile communication terminals, userequipment (UE), mobile equipment (ME), and other devices that supportvarious types of wireless communication technologies.

Embodiments of the present invention relate to sending and receivingdata between a base station (e.g. Node B, eNB, access point, etc.) and amobile station (e.g. mobile terminal, UE, user device, etc.) in a LongTerm Evolution (LTE) system. Power consumption of the mobile terminalcan be reduced to a minimum and a downlink channel can be moreeffectively monitored because a reception time for the downlink channelis determined according to the characteristics of a preamble for amobile terminal that performs random access.

Second generation (2G) mobile communications relate to transmitting andreceiving voice signals in a digital manner, and include technologiessuch as CDMA, GSM, and the like. As an enhancement from GSM, GPRS wasdeveloped to provide packet switched data services based upon GSM.

Third generation (3G) mobile communications relate to transmitting andreceiving not only voice signals, but also video and data. The 3GPP(Third Generation Partnership Project) developed the IMT-2000 mobilecommunication system and selected WCDMA as its radio access technology(RAT). The combination of IMT-2000 and WCDMA can be referred to as UMTS(Universal Mobile Telecommunications System), which comprises a UMTSTerrestrial Radio Access Network (UTRAN).

As data traffic is expected to increase dramatically, thestandardization for 3rd generation mobile communications is underway toestablish a Long-Term Evolution (LTE) network that supports greaterbandwidth. LTE technologies are employed for an Evolved-UMTS (E-UMTS),which has an Evolved-UTRAN (E-UTRAN) that uses OFDMA (OrthogonalFrequency Division Multiple Access) as its radio access technology(RAT).

FIG. 1 shows the exemplary network architecture for an E-UMTS (EvolvedUniversal Mobile Telecommunications System) 100, which is a type ofmobile communications system. The E-UMTS system is a system that hasevolved from the UMTS system and its basic standardization tasks are nowbeing performed by the 3GPP organization. The E-UMTS system can be saidto be a Long Term Evolution (LTE) system, which is a type of so-called4G or next generation system that has evolved from the current 3G mobilecommunication systems.

The E-UMTS network 100 can be generally distinguished into the E-UTRAN(Evolved Universal Terrestrial Radio Access Network) 110 and the CN(core network). The E-UTRAN is comprised of a mobile terminal 112 (e.g.user equipment (UE), mobile station, handset, mobile phone, etc.), abase station 114, 116, 118 (e.g., an eNode B, access point (AP), networknode, etc.) a serving gateway (S-GW) 122, 124 located at an end of thenetwork for connection with an external network, and a mobilitymanagement entity (MME) 122, 124 that manages various mobility aspectsof the mobile terminal. For a single eNode B, one or more cells (orregions, areas, etc.) may exist.

FIGS. 2 and 3 show the radio interface protocol between the mobileterminal and base station based on the 3GPP radio access networkstandard. This radio interface protocol is divided horizontally into aphysical layer, a data link layer, and a network layer, and is dividedvertically into a user plane for transmitting data information and acontrol plane for transferring control signals (signaling). Theseprotocol layers can be divided into L1 (Layer 1), L2 (Layer 2), and L3(Layer 3), which are the lower three layers of the OSI (Open SystemInterconnection) standard model, which is well known in communicationsystems.

Hereafter, the control plane of the radio protocol in FIG. 2 and theuser plane of the radio protocol in FIG. 3 will be describedrespectively.

In Layer 1, the physical layer 225-245, 325-345 uses one or morephysical channels to provide an information transfer service. Thephysical layer is connected to the MAC (Medium Access Control) layer224-244, 324-344 located above via one or more transport channels, anddata is transferred between the MAC layer and the physical layer throughthese transport channels. Also, between respectively different physicallayers, such as the physical layer in the transmitter (transmittingside) and the physical layer in the receiver (receiving side), data istransferred via one or more physical channels.

The physical channels that exist for the physical layer in thetransmitting side and in the receiving side include: SCH(Synchronization Channel), PCCPCH (Primary Common Control PhysicalChannel), SCCPCH (Secondary Common Control Physical Channel), DPCH(Dedicated Physical Channel), PICH (Paging Indicator Channel), PRACH(Physical Random Access Channel), PDCCH (Physical Downlink ControlChannel) and PDSCH (Physical Downlink Shared Channel) and the like.

In Layer 2, the MAC layer provides service to a RLC (Radio Link Control)layer 223-243, 323-343, which is an upper layer, via one or more logicalchannels. Such logical channels can be classified according to the typeof data being transmitted, whereby control channels are used to transmitcontrol plane information and traffic channels are used to transmit userplane information.

The RLC layer supports the transmission of data with reliability. Eachradio bearer (RB) guarantees a particular QoS (Quality of Service) andhandles the transmission of data associated thereto. In order for theRLC layer to guarantee the QoS that is unique to that RB, one or moreRLC entities are provided for each RB. Also, several RLC modes (TM:Transparent Mode, UM: Unacknowledged Mode, AM: Acknowledged Mode) areprovided to support various QoS requirements.

The PDCP (Packet Data Convergence Protocol) layer 322-342 in Layer 2performs a header compression function to reduce the header size forInternet Protocol (IP) packets that contain relatively large andunnecessary control information such that IP packets (such as for IPv4,IPv6, etc.) may be effectively transmitted over the radio interfacehaving relatively small bandwidth. Also, the PDCP layer is used forperforming coding of control plane (C-plane) data, such as RRC messages.The PDCP layer can also perform coding of user plane (U-plane) data.

Located at the uppermost portion of Layer 3, the RRC (Radio ResourceControl) layer 222-242 is only defined in the control plane and isresponsible for the control of logical channels, transport channels andphysical channels with relation to the configuration, re-configurationand release of radio bearers (RBs). Here, a radio bearer is a serviceprovided by Layer 2 for transferring data between the mobile terminaland E-UTRAN.

With reference to FIG. 4, a method for the mobile terminal in an LTEsystem to receive downlink data will be explained.

On the downlink, there are basically two types of physical channels:PDCCH and PDSCH. The PDCCH is not directly related to transmitting userdata, but used in transmitting control information needed forimplementing (or using) physical channels. In more basic terms, it canbe said that the PDCCH is used in controlling other physical channels.In particular, the PDCCH is used in transmitting information necessaryfor the mobile terminal to receive the PDSCH. With respect to data thatis transmitted at a particular point in time using a particularfrequency bandwidth, information about what mobile terminal such data isintended for, the size of such data being transmitted, and the like istransmitted via the PDCCH. Accordingly, each mobile terminal receivesthe PDCCH at a particular time (e.g., TTI: transmission time interval)and checks whether any data (that should be received) was transmitted.If there is an indication that data (which should be received) wasindeed transmitted, the PDSCH is additionally received by using theinformation (such as the appropriate frequency, etc.) indicated by thePDCCH. It can be said that information indicating as to what mobileterminal (i.e. a single UE or multiple UEs) the data of the PDSCH isbeing transmitted to, information indicating how the mobile terminal(s)should receive and decode the PDSCH data, and the like are transmittedvia a physical channel, i.e. the PDCCH (Physical Downlink ControlCHannel).

For example, in a particular sub-frame, let us assume that radioresource information A (e.g. frequency location), transmission formatinformation B (e.g. transmission block size, modulation and codinginformation, etc.), and RNTI (Radio Network Temporary Identity)information C undergo CRC (Cyclic Redundancy Check) masking andtransmitted via the PDCCH. One or more mobile terminals in acorresponding cell use the RNTI information that it has in order tomonitor the PDCCH, and referring to the above assumption, for a mobileterminal having RNTI information C, when the PDCCH is decoded, CRCerrors do not occur. Accordingly, such mobile terminal uses thetransmission format information B and radio resource information A todecode the PDSCH in order to receive data. In contrast, with respect tothe above assumption, in a mobile terminal that does not have RNTIinformation C, CRC errors occur when the PDCCH is decoded, and thus suchmobile terminal does not receive the PDSCH.

Through the above procedures, in order to inform about which mobileterminals have been allocated radio resources, a RNTI (Radio NetworkTemporary Identifier) is transmitted via each PDCCH, and such RNTI canbe classified as a dedicated RNTI or a common RNTI. A dedicated RNTI isallocated to a single mobile terminal and is used for transmitting andreceiving data corresponding to that mobile terminal. Such dedicatedRNTI is only allocated to those mobile terminals having theirinformation registered in the base station (eNB). In contrast, a commonRNTI is used by those mobile terminals that do not have theirinformation registered in the base station (eNB) and cannot be allocateda dedicated RNTI, in order to send and receive data with the basestation or used for transmitting information (such as systeminformation) that is commonly applied to a plurality of mobileterminals.

Meanwhile, the two main elements that comprise the E-UTRAN are the basestation and the mobile terminal. The radio resources for a single cellare comprised of uplink radio resources and downlink radio resources.The base station is responsible for the allocation and control of uplinkradio resources and downlink radio resources of a cell. Namely, the basestation determines what radio resources are to be used by what mobileterminals at certain moments in time. For example, the base station candetermine that 3.2 seconds from now, the frequency from 100 Mhz to 101Mhz will be allocated to user 1 for a duration of 0.2 seconds to allowdownlink data transmissions. Also, after the base station makes suchdetermination, these matters can be informed to the corresponding mobileterminal such that this mobile terminal receives downlink data Likewise,the base station can determine when a certain mobile terminal should usewhat amount of which radio resources for data transmission via theuplink, and the base station informs the mobile terminal about itsdetermination, to thus allow the mobile terminal to transmit data duringthe determined time period using the determined radio resources.

Unlike the related art, if the base station manages radio resources in adynamic manner, efficient use of radio resources would be possible.Typically, a single mobile terminal continuously uses a single radioresource during a call connection. This is not preferable consideringthat most recent services are IP packet-based. The reason is that mostpacket services do not continuously generate packets during the durationof a call connection, and there are many time periods in which nothingis transmitted during the call. Despite this, continued allocation of aradio resource to a single mobile terminal is inefficient. To solvethis, the mobile terminal of a E-UTRAN system uses a method in whichradio resources are allocated to the mobile terminal only while servicedata exists.

Hereafter, aspects of the RACH (Random Access CHannel) procedure will beexplained. The RACH procedure is used for transmitting relatively shortlength data via the uplink. In particular, the RACH is used when thereis a signaling message or user data to be transmitted via the uplink bya mobile terminal that did not receive allocation of dedicated radioresources, or may also be used when the base station should instruct themobile terminal to perform a RACH procedure.

Next, the random access procedure provided in an LTE system will beexplained. The random access procedure provided in the LTE system can beclassified as a contention based random access procedure and anon-contention based procedure. Such classification is based uponwhether the random access preamble is selected by the mobile terminalitself (i.e. preamble selected by the MAC in the mobile terminal) orselected by the base station (i.e. receiving information about thepreamble to be used through explicit signaling).

In a non-contention based random access procedure, the mobile terminaluses the preamble that was directly allocated to it from the basestation. Thus, if the base station had allocated a particular randomaccess preamble to the mobile terminal, such random access preamble isonly used by that mobile terminal, while other mobile terminals do notuse such random access preamble. Accordingly, because there is aone-to-one (1:1) relationship between the random access preamble and themobile terminal that uses such random access preamble, there are nocontentions (or conflicts) between multiple mobile terminals. In suchcase, upon receipt of such random access preamble, the base station canimmediately know which mobile terminal transmitted such random accesspreamble, and thus it can be said that more efficient operation ispossible.

In contrast, for a contention based random access procedure, because themobile terminal sends transmission upon selecting a particular randomaccess preamble among those that may be used, there is the possibilitythat multiple mobile terminals use the same random access preamble.Thus, even upon reception of a particular random access preamble, thebase station cannot accurately know which mobile terminal transmitted onsuch random access preamble.

The mobile terminal performs a random access procedure for at least thefollowing exemplary situations:

-   -   upon performing an initial access when there is no radio        resource control (RRC) connection with the base station;    -   upon initial access to a target cell while the mobile terminal        is in handover;    -   upon request by a command of the base station;    -   upon generation of data for the uplink, when uplink time        synchronization is not correct or when designated radio        resources to be used in appropriate requesting radio resources        have not yet been allocated;    -   during a correction (e.g. decoding, reconstruction, recovery,        etc.) procedure when there is a radio link failure or handover        failure.

Based upon the above explanations, the operations between the mobileterminal and the base station for a contention based random accessprocedure will be explained with reference to FIG. 5 (that includessteps 1 through 4).

Step 1)

In a contention based random access procedure, the mobile terminalselects (e.g. at random) one random access preamble among a set ofrandom access preambles indicated via system information or a handovercommand, then selects PRACH resources that can be used to transmit suchrandom access preamble, and then performs transmission. Here, suchpreamble is called a RACH MSG 1. When the mobile terminal itself(“randomly”) selects the preamble (i.e. the preamble selected by the MACitself), such is called a contention-based RACH procedure, and thepreamble is called a contention-based preamble. If the mobile terminalreceives allocation of the preamble directly from the network throughthe RRC or PDCCH (i.e. an explicitly signaled preamble), this is calleda non-contention based RACH procedure, and such preamble is called adedicated preamble.

Step 2)

After transmitting the random access preamble as selected above, themobile terminal attempts to receive its random access response within arandom access response reception window indicated from the base stationvia system information or handover command. In more detail, the randomaccess response information (typically called a RACH MSG 2) istransmitted in the form of a MAC PDU, which is delivered via the PDSCH,and the information related to the radio resources for the PDSCH isdelivered through the PDCCH via the RA-RNTI.

The random access response includes values comprising a random accesspreamble identifier (ID), a UL Grant (for uplink radio resources), aTemporary C-RNTI (a temporary cell identifier), and a Time AlignmentCommand (a value for time synchronization adjustment).

If the random access preamble identifier (ID) is the same as (i.e.matches) the random access preamble transmitted in step 1) above,especially while a contention based random access preamble procedure isin progress, the mobile terminal uses the information related to theuplink radio resources and performs the following step 3). If adedicated preamble is used in step 1), and if the random access preambleidentifier (ID) included in RACH MSG 2 and the random access preambletransmitted by the mobile terminal in step 1) are the same (i.e.matches), the RACH procedure is considered to be ended or terminated.

Step 3)

If the mobile terminal receives a random access response (RAR) that ismeant for itself (i.e. the RAR is a valid response for that mobileterminal), the information within such random access response isprocessed, respectively. Namely, the mobile terminal applies the TimeAlignment Command and stores the Temporary C-RNTI. Also, the UL Grant isused to transmit the data stored in its buffer or to transmit newlygenerated data to the base station. Here, the data transmitted by usingthe UL Grant (i.e., the MAC PDU) is commonly called RACH MSG 3. Amongthe data (i.e. RACH MSG 3) included in the UL Grant, the mobile terminalidentifier (ID) must be included. This is because in a contention basedrandom access procedure, the base station cannot determine which mobileterminal performed such random access procedure, and in order to preventor resolve any future contentions or conflicts, information that can beused to identify the mobile terminal would be required.

In the above procedure, there are two ways to include the identifier forthe mobile terminal. For the first way, if the mobile terminal alreadyhas a valid cell identifier (C-RNTI) allocated from the base station(eNB) of the corresponding cell before the random access procedure isperformed, the mobile terminal transmits such cell identifier via the ULGrant. For the second way, if the mobile terminal did not receiveallocation of a unique cell identifier from the eNB, the mobile terminalincludes its core network identifier (e.g., S-TMSI, Random ID, etc.) andperforms transmission. After transmitting data using the UL Grant, themobile terminal starts a contention resolution timer in order to solveany contention (conflict) problems.

Step 4)

After transmitting data (that includes its identifier) using the ULGrant included in the random access response, the mobile terminal waitsfor commands from the base station for resolving contentions. Namely,reception of the PDCCH is attempted in order to receive a particularmessage. There are two ways to receive the PDCCH. As stated previously,if the identifier transmitted by using the UL Grant is a cell identifier(C-RNTI) allocated to the mobile terminal from the eNB, the mobileterminal attempts reception of the PDCCH by using its cell identifier,and if the identifier is an identifier that was allocated through thecore network, attempt to receive the PDCCH is performed by using theTemporary C-RNTI included in the random access response.

Afterwards, for the former case (i.e. C-RNTI), if the PDCCH (referred toa RACH MSG 4 hereafter) is received (by using its cell identifier)before expiration of the contention resolution timer, then it isconsidered that the mobile terminal performed the ransom accessprocedure in a normal manner and the random access procedure is ended(terminated). For the latter case (i.e. Temporary C-RNTI), if the PDCCHwas received through the temporary cell identifier before expiration ofthe contention resolution timer, the data (referred to as RACH MSG 4hereafter), which is delivered by the PDSCH that is indicated by thePDCCH, is checked. If such data contains a unique identifier for themobile terminal itself, it is considered that the mobile terminalperformed the random access procedure in a normal manner, and the randomaccess procedure is ended (terminated). The message or MAC PDU receivedin this step 4) is commonly called RACH MSG 4.

Step 5)

In case the contention resolution timer has expired (i.e., a TemporaryC-RNTI or a cell identifier for the mobile terminal is not receivedbefore expiration of the contention resolution timer), the mobileterminal considers the RACH procedure to be a failure. As a result, anappropriate back-off timer is operated (started) and the RACH procedurebeginning from step 1) above is started again after expiration of suchback-off timer.

With reference to the technical description thus far, the technicalsolution provided by the embodiments of the present invention can bedescribed as follows.

The mobile terminal receives parameters, which are to be used in theRACH procedure, from the upper layer (i.e. the RRC layer) during theinitialization time of a call. However, as described above, the RACHprocedure is used by a mobile terminal (which has not receivedallocation of dedicated radio resources) in order to request resourcesfrom the base station. Because the RACH procedure is used by anunspecified mobile terminal to request the base station for allocationof radio resources, the various parameters related to the physicalchannels and the like used for the RACH procedure are not optimized forany particular mobile terminal, but are set based on estimate values andthe like upon considering the average for multiple mobile terminals.This means that the parameters used for the RACH procedure are notoptimal for each respective mobile terminal, and thus there is a highprobability of failure for the RACH procedure. Accordingly, the RACHprocedure started by the mobile terminal should generally be repeatedseveral times until success is actually achieved.

However, for a mobile terminal located in a specific area or in aparticular state, repeated attempts of the RACH procedure results in awaste of radio resources or cause delays in data delivery. For example,for a mobile terminal located at the boundary region of two adjacentcells, and if the mobile terminal has accessed a cell that has adetrimental signal environment, when the RACH procedure attempts arecontinuously repeated, such mobile terminal will have a high probabilityof experiencing continuous RACH procedure failures.

Due to such reasons, if the RACH procedure fails, it would be better ifthe mobile terminal performs cell reselection or re-attempts callestablishment. To do so, the MAC entity has a counter that counts thenumber of times that a particular RACH procedure has been attempted.Also, if the number of RACH procedure attempts exceeds a particularthreshold, the MAC entity informs the RRC entity that there is a problemin the PRACH procedure.

The RACH procedure will be further explained as follows with referenceto FIG. 6 (that includes steps 0 through 4) and FIG. 7.

Step 0)

The MAC entity receives, from the upper layer (RRC), parameters relatedto the RACH procedure and initializes the variables related to the RACHprocedures. In this process, the Preamble Transmission counter value isinitialized. A Preamble Transmission maximum value is received from theupper layer.

Step 1)

A RACH Preamble is selected. The Preamble Transmission counter value iscompared with the Preamble Transmission maximum value. If the PreambleTransmission counter value equals the Preamble Transmission maximumvalue+1, the RRC entity is informed that the RACH procedure has problem.The selected RACH Preamble is transmitted.

Step 2)

A RACH Response (RAR) with respect to the RACH Preamble transmitted instep 1) is received. If the RACH Response reception fails, the PreambleTransmission counter value is increased by 1, and a back-off time isapplied if necessary, and the process returns back to step 1).

Step 3)

Transmission is performed based upon the radio resource informationindicated in the received RACH Response.

Step 4)

Contention resolution is performed by using a timer, mobile terminalidentifiers, and the like. If contention resolution fails, the PreambleTransmission counter value is increased by 1, and a back-off time isapplied if necessary, and the process returns back to step 1).

FIG. 7 shows a flowchart of an exemplary RACH procedure operation ofaccording to a first embodiment.

Upon starting the RACH procedure, reception and initialization isperformed (S110). Namely, the MAC layer (entity) of the UE receives aRACH request from the network (i.e. an upper layer) (S111). Thereafter,the RACH parameters are initialized and the preamble transmit counter isset to 1 (S112).

Here, the transmit (transmission) counter for the random access preamble(or RACH preamble) is initialized. Also, a preamble transmission maximumvalue is received from the upper layer.

Next, procedures regarding the RACII preamble are performed (S120).Namely, the UE MAC selects a RACH preamble (S121) among a set ofpreambles delivered from the upper layer (RRC). Here, the RACH preambleis also known as RACH MSG 1. If the UE has selected the RACH preamble atrandom, such is referred to as a contention based RACH procedure, whilesuch selected preamble is called a contention based preamble. Then, thepreamble transmit counter value is compared with the preamble transmitmaximum value+1 (S122). If the preamble transmit counter value is lessthan the preamble transmit maximum value+1, then the preamble istransmitted (S123). However, if the preamble transmit counter valueequals the preamble transmit maximum value+1, then a RACH problem isreported to the upper layer (RRC) (S124).

After transmitting the selected preamble, the UE (100) checks to see ifa random access response (RAR: RACH response with respect to thetransmitted preamble) indicated from the eNB (200) via systeminformation or handover command is received within a response receptionwindow or a TTI window (S130).

Namely, the RAR is transmitted in the form of a MAC PDU and deliveredvia a PDSCH (Physical Downlink Shared CHannel). Also, controlinformation is transmitted via the PDCCH (Physical Downlink ControlCHannel) to allow the UE to appropriately receive the PDSCH. Thus, thePDCCH information includes information about the UE that should receivethe PDSCH, information about the frequency and time of the radioresources for the PDSCH, and information about the transmission formatof the PDSCH.

If the UE successfully receives the PDCCH, the RAR delivered via thePDSCH can be appropriately received by using the PDCCH information.Here, the RAR includes a RACH ID, UL grant, Temporary C-RNTI, and TimeAlignment commands.

If the UE successfully received the RAR and a preamble match isverified, a RACH MSG 3 is transmitted (S140). However, if either the RARis not received or if there is no preamble match, then the preambletransmit counter is incremented by 1 (S131) and the procedure returnsback to preamble selection (S121). Here, a back-off time may be appliedif needed (S125).

Upon successfully receiving the RAR, the UE then proceeds to process theinformation included therein. Also, by using the UL grant, the UE (100)sends to the eNB (200) the data stored in its buffer or newly generateddata (S140). Here, the data delivered via the UL grant is called RACHMSG 3. Among the data included in the UL grant, a UE identifier must beincluded. Such data is delivered via the CCCH (Common Control CHannel)in the form of an SDU. Also, such data is delivered via a MAC ControlElement that includes a C-RNTI.

Thereafter, the UE starts a timer related to whether or not transmissionwas successful, and waits for a response with respect to suchtransmitted data. Before the timer expires, if a response that includesthe UE ID is received (i.e. if contention resolution is successful), thedata transmission is considered to be successful (S150). Thus, suchreception of a response means that a contention resolution identity MACcontrol element has been received. Alternatively, it may mean that theC-RNTI was received by the UE via the PDCCH or mean that new uplinkresources have been allocated.

However, if a response is not received upon expiry of the timer or ifthe UE does not receive a response that includes the UE ID, then thepreamble transmit counter is increased by 1 and the process returns tostep S121, with a back-off time being applied if necessary.

Meanwhile, if the RACH procedure continues to fail, the UE shouldre-select a cell or re-attempt the call connection. To do so, the MACentity in the UE includes a counter means, which counts how many timesthe RACH procedure had been attempted. If a certain number of attemptshave been made but without success, a problem in the RACH procedure maybe reported to the RRC (upper) layer.

In such RACH procedure operation, the mobile terminal, with respect tothe selected R ACH preamble, performs a comparison value (prior totransmitting the R ACH preamble) between the Preamble Transmissioncounter value and the Preamble Transmission maximum. If the PreambleTransmission counter value exceeds the Preamble Transmission maximum, itis reported to the upper layer that there is a problem in the RACHprocedure. In actuality, the operations of steps 1 through 4 arerepeated for the RACH procedure, and in step 1) of the first embodiment,the MAC entity determines whether there are any problems in the RACHprocedure, and if there is a problem, such is reported to the upperlayer.

However, the first embodiment does not consider variables orcircumstances such as back-off time, and thus results in inefficientRACH recovery (or restoration) procedures. Namely, in the firstembodiment, at the time when the RACH procedure fails, it is not checkedas to how many times the RACH procedure has failed. Instead, the numberof failures of the RACH procedure is checked only at the time whenstep 1) is newly performed in order to determine whether there is aproblem in the RACH procedure. Accordingly, from the time when a failureis detected, and depending upon the time period required until step 1)of the RACH procedure begins, the mobile terminal requires time toconclude that the RACH procedure has a problem and reporting to theupper layer about such problem is delayed. If the mobile terminal iswithin a detrimental radio environment, such as when the user (with hismobile terminal) is within an elevator, traveling through a tunnel,etc., there is an increase in the probability of various types ofproblems occurring, such as delays in performing re-access to a cellhaving a better quality signal environment, disconnection of the call,suffering data loss, or the like.

Namely, the first embodiment is implemented on the basis of the mostfavorable conditions, whereby there is no time gap or delay from when aRACH procedure failure is detected until a new step 1) of the RACHprocedure is performed. But in actuality, i.e., under less favorableconditions, problems may arise. Under realistic conditions, the back-offtime results in a time delay between the time when RACH procedurefailure is detected and when a new RACH procedure step 1) is performed.Also, radio resources that can be used for transmitting the RACHpreamble are allocated at periodic time intervals (e.g. the fastestallocation occurring at every 10 ms). So, depending on when the mobileterminal detects the RACH procedure failures during such 10 ms interval,the actual time delay until step 1) is re-performed can vary.

Here, the back-off time refers to the time period during which themobile terminal must wait until the next RACH procedure begins after afailure in a current RACH procedure is detected. Such back-off time isuseful if the there is a high number of mobile terminals performing RACHprocedures for a certain cell. Namely, in case of a congested cell, whennumerous mobile terminals respectively perform continuous RACHprocedures without any waiting time, the RACH attempts for each mobileterminal will continue to fail. To avoid such situations, it would beadvantageous if some mobile terminals briefly wait to perform subsequentRACH procedure attempts, such that the number of mobile terminalsattempting to transmit their RACH preambles at the same time can bereduced, which results in less congestion.

To address such problems, a second embodiment (as shown in FIG. 8)provides a faster procedure for determining whether there are anyproblems in the RACH procedure, and if there is a problem, such can bereported to the upper layer more quickly and handled more effectively,which results in improved call quality. In more detail, in order toquickly determine whether or not the RACH procedure has a problem, it isproposed that failures in the RACH procedure are to be used.

If a failure occurs in the RACH procedure, certain operations areperformed according to such failure. Also, it is determined whether theproblem in the RACH procedure occurred at the point in time of suchfailure, and according to such determination, the occurrence of suchproblem is reported to the upper layer.

A failure in the RACH procedure may denote the situation when the mobileterminal fails its contention resolution procedure. Also, a failure inthe RACH procedure may denote the situation when the mobile terminal,having transmitted a RACH Preamble, does not receive a RACH AccessResponse (RAR) with respect to the RACH Preamble within a particulartime period.

Determining whether a problem in the RACH procedure occurs may denote acomparison between the number of RACH cycles performed by the mobileterminal and the maximum value for RACH cycles. If the mobile terminalperformed more RACH cycles than the maximum number of RACH cycles, it isdetermined that there is a problem in the RACH procedure. If the numberof RACH cycles performed by the mobile terminal equals the maximumnumber of RACH cycles+1, it is determined that there is a problem in theRACH procedure.

The number of RACH cycles is the Preamble Transmission counter value.The RACH cycle maximum value is the Preamble Transmission max value. TheRACH cycle number is initialized when instructions are received from theMAC entity or from an external source to perform the RACH procedure.

Failure of contention resolution means that contention resolution hasnot succeeded upon expiration of contention resolution time. Success ofcontention resolution means the situation where, if the mobile terminaltransmitted a CCCH SDU, the corresponding contention resolution identityMAC control element is received. Success of contention resolution meansthe situation where, if the mobile terminal transmitted a C-RNTI MACControl element, the C-RNTI of the mobile terminal is received via thePDCCH and new uplink radio resources are allocated.

The RACH procedure according to the second embodiment will be furtherexplained as follows with reference to FIG. 8 (that includes steps 0through 4).

Step 0)

The MAC entity receives, from the upper layer, parameters related to theRACH procedure and initializes the variables related to the RACHprocedures. In this process, the

Preamble Transmission counter value is initialized. A PreambleTransmission maximum value is received from the upper layer.

Step 1)

A RACH Preamble is selected. The selected RACH Preamble is transmitted.

Step 2)

A RACH Response (RAR) with respect to the RACH Preamble transmitted instep 1) is received. If the RACH response is not received within thespecified time period or if the received RACH response does not includea value that matches the preamble transmitted by the mobile terminal,the preamble transmission counter value is increased by 1. Also, thepreamble transmission counter value is compared with the preambletransmission maximum value. If the preamble transmission counter valueequals the preamble transmission maximum value+1, the RRC is informedthat a RACH problem has occurred. Also, after a back-off time is appliedif necessary, the process returns and begins again from step 1).

Step 3)

Transmission is performed based upon the radio resource informationindicated in the RACH Response received in step 2).

Step 4)

Contention resolution is performed by using a timer, mobile terminalidentifiers, and the like. If contention resolution fails, the PreambleTransmission counter value is increased by 1. Also, the preambletransmission counter value is compared with the preamble transmissionmaximum value. If the preamble transmission counter value equals thepreamble transmission maximum value+1, the RRC is informed that a RACHproblem has occurred. Also, after a back-off time is applied ifnecessary, the process returns and begins again from step 1).

In more detail, FIG. 8 shows an exemplary operation according to theembodiments described herein. As can be seen, it is checked whether aRACH problem can be determined right at the time when RACH procedurefailure is detected, and such is reported to the upper layer.Accordingly, as a result, by allowing the mobile terminal to quicklydetect RACH problems, such problems in the RACH procedure can be quicklyresolved, and call reliability can be increased.

In the second embodiment, the steps S210, S211, S212 and S220 are thesame as or similar to the steps S110, S111, S112 and S121 of the firstembodiment. However, the following procedures labeled as S230 (thatincludes S231, S231, S233, S234, S235) and S240 and S250 are a bitdifferent in their sequence of being performed.

Namely, after the preamble is selected and transmitted (S220), a checkas to whether the RAR is received and whether there is a preamble matchare performed (S231). If both conditions are satisfied, a RACH MSG 3 istransmitted (S240), then contention resolution is performed (S250).

If both conditions in S231 (i.e. RAR received and preamble match) arenot satisfied, or if contention resolution is unsuccessful at S250, theprocess goes to step S232, in which the preamble transmit counter isincremented by 1.

Then, the preamble transmit counter is compared with the preambletransmit counter maximum value+1. If these two values are equal, a RACHproblem is reported to the upper layer (RRC) (S234) and the processreturns to S220 (i.e. preamble selection and transmission). Otherwise,namely, if the preamble transmit counter is not equal to the preambletransmit counter maximum value+1, then the process returns to S220.Here, a back-ff time may be applied if necessary (S235).

As a result of the second embodiment, a faster procedure for determiningwhether there are any problems in the RACH procedure is achieved, and ifthere is a problem, such can be reported to the upper layer more quicklyand handled more effectively.

FIG. 9 shows an exemplary structure block diagram of a UE (100) and eNB(200) according to the first and second embodiments.

The UE comprises a storage means (101), a control means (102) and atransceiver (103). Similarly, the eNB comprises a storage means (201), acontrol means (202) and a transceiver (203). Such storage means (101,201) may be configured to store the procedures as shown in FIGS. 6through 8 for the first and second embodiments. The control means (102,202) provide control to the storage means (101, 201) and thetransceivers (103, 203), such that the procedures stored in the storagemeans (101, 201) are performed with appropriate signal transmission andreception via the transceivers (103, 203).

Some more details about the concepts and features of the inventiveembodiments described herein can also be summarized as follows.

The DRX Command MAC CE may be used to put a UE directly into eithershort or long DRX Cycle. But when a DRX Command MAC CE is received whilethe DRX Short Cycle Timer is running, the timer should not be affected.If the timer is started again (i.e. re-started), the UE is further putin wake-up state, causing more battery consumption. This situation canoccur when HARQ Re-transmission Grant for a MAC PDU which includes theDRX Command MAC CE is received while the Short DRX Cycle Timer isrunning. Here, the terms “start” and “re-start” may be distinguishedsuch that “start” is used when the timer is not running, while“re-start” is used when the timer is running. Thus, when the Short DRXCycle Timer is running, it cannot be started, but it can be restarted.

However, such potential problem may be avoided by implementing thefollowing concept: when DRX Command MAC CE is received while Short DRXCycle Timer is running, the MAC CE is ignored.

The Active Time may include “a PDCCH indicating a new transmissionaddressed to the C-RNTI or Temporary C-RNTI of the UE has not beenreceived after successful reception of a Random Access Response (RAR).”This would cover the period between the time of RAR reception and thetime of starting the contention resolution timer. Otherwise, the UEwould monitor the DL channels longer than needed. For example, evenafter the contention resolution timer expires due to reception of notemporary C-RNTI, the UE would still monitor the DL channels.

However, such potential problem may be avoided by implementing thefollowing: setting the Active Time to include the period between thetime of successful reception of RAR and the time of starting theContention Resolution timer (for the case of contention-based preamble).

In other words, the situations for a contention-based preamble can beclarified as above. If UE has to wake up until the reception of C-RNTIregardless of other problems, the features described herein can beapplied to situations for a dedicated preamble .

The maintenance of Uplink Time Alignment will be explained.

The UE may have a configurable Time Alignment Timer. The Time AlignmentTimer is valid only in the cell for which it was configured and started.

If the Time Alignment Timer has been configured, the UE shall:

-   -   when a Timing Advance MAC control element is received:        -   apply the Timing Advance Command;        -   start the Time Alignment Timer (if not running) or restart            the Time Alignment Timer (if already running).    -   when a Time Alignment Command is received in a Random Access        Response message:        -   if the Random Access Preamble and PRACH resource were            explicitly signalled:            -   apply the Time Alignment Command;            -   start the Time Alignment Timer (if not running) or                restart the Time Alignment Timer (if already running).    -   else, if the Time Alignment Timer is not running or has expired:        -   apply the Time Alignment Command;        -   start the Time Alignment Timer;        -   when the contention resolution is considered not successful,            stop the Time Alignment Timer.    -   else:        -   ignore the received Time Alignment Command.    -   when the Time Alignment Timer has expired or is not running:        -   prior to any uplink transmission, use the Random Access            procedure in order to obtain uplink Time Alignment.    -   when the Time Alignment Timer expires:        -   release all PUCCH resources;        -   release any assigned SRS resources.

Discontinuous Reception (DRX) will be explained. The UE may beconfigured by the RRC with a DRX functionality that allows it to notcontinuously monitor the PDCCH. The DRX functionality consists of a LongDRX cycle, a DRX Inactivity Timer, a DRX Retransmission Timer, andoptionally a Short DRX Cycle and a DRX Short Cycle Timer.

When a DRX cycle is configured, the Active Time includes the time:

-   -   while the On-Duration Timer or the DRX Inactivity Timer or a DRX        Retransmission Timer or the Contention Resolution Timer is        running; or    -   while a Scheduling Request is pending; or    -   while an uplink grant for a retransmission can occur; or    -   from the successful reception of a Random Access Response (RAR)        to the starting of the Contention Resolution Timer.

Here, the Active Time can also be defined as:

-   -   while a PDCCH indicating a new transmission addressed to the        C-RNTI of the UE has not been received after successful        reception of a Random Access Response, if the Random Access        Preamble was explicitly signaled; or    -   while the DL resuming timer is running. The DL resuming timer is        started when successful RAR is received in case that the Random        Access Preamble was explicitly signaled; (here, the DL resuming        timer is stopped when the C-RNTI of the UE is received)        (instead, it is also possible that the DL-resolution timer is        started when a dedicated preamble is received over the PDCCH)        or,    -   from the successful reception of a Random Access Response (RAR)        to the starting of the Contention Resolution Timer, if the        Random Access Preamble was selected by the UE MAC.

When a DRX cycle is configured, the UE shall perform the followingprocedures for each sub-frame:

-   -   start the On Duration Timer when [(SFN * 10)+sub-frame number]        modulo (current DRX Cycle)=DRX Start Offset;    -   if a HARQ RTT Timer expires in this sub-frame and the data in        the soft buffer of the corresponding HARQ process was not        successfully decoded:        -   start the DRX Retransmission Timer for the corresponding            HARQ process.    -   if a DRX Command MAC control element is received:        -   stop the On Duration Timer;        -   stop the DRX Inactivity Timer.    -   if the DRX Inactivity Timer expires or a DRX Command MAC control        element is received in this sub-frame:        -   if the short DRX cycle is configured:            -   if the DRX Short Cycle Timer is not running, start the                DRX Short Cycle Timer;            -   use the Short DRX Cycle.        -   else:            -   use the Long DRX cycle.    -   if the DRX Short Cycle Timer expires in this sub-frame:        -   use the long DRX cycle.    -   during the Active Time, for a PDCCH-sub-frame except if the        sub-frame is required for uplink transmission for half-duplex        FDD UE operation:        -   monitor the PDCCH;        -   if the PDCCH indicates a DL transmission:            -   start the HARQ RTT Timer for the corresponding HARQ                process;            -   stop the DRX Retransmission Timer for the corresponding                HARQ process.        -   if the PDCCH indicates a new transmission (DL or UL):            -   start or restart the DRX Inactivity Timer.        -   if a DL assignment has been configured for this sub-frame            and no PDCCH indicating a DL transmission was successfully            decoded:            -   start the HARQ RTT Timer for the corresponding HARQ                process.    -   when not in active time, CQI and SRS shall not be reported.        Regardless of whether the UE is monitoring PDCCH or not the UE        receives and transmits HARQ feedback when such is expected.

The inventive embodiments described herein can further be described asfollows.

If no Random Access Response is received within the TTI window[RA_WINDOW_BEGIN—RA_WINDOW_END], or if all received Random AccessResponses contain Random Access Preamble identifiers that do not matchthe transmitted Random Access Preamble, and the Random Access Responsereception is considered not successful, the UE shall:

if the Random Access procedure was initiated by the MAC sub-layeritself; or if the Random Access procedure was initiated by a PDCCH orderand the PREAMBLE TRANSMISSION COUNTER<PREAMBLE TRANS MAX: then incrementPREAMBLE_TRANSMISSION_COUNTER by 1;

if PREAMBLE TRANSMISSION COUNTER=PREAMBLE TRANS MAX+1: indicate (orreport) a Random Access problem to upper layers.

-   -   if in this Random Access procedure:    -   the Random Access Preamble was selected by MAC; or    -   the Random Access Preamble and PRACH resource were explicitly        signaled and will expire before the next available Random Access        occasion:    -   based on the back-off parameter in the UE, compute and apply a        back-off value indicating when a new Random Access transmission        shall be attempted;    -   proceed to the selection of a Random Access Resource.

In other words, if the Contention Resolution is considered to beunsuccessful, the UE shall:

-   -   if the Random Access procedure was initiated by the MAC        sub-layer itself; or    -   if the Random Access procedure was initiated by a PDCCH order        and the PREAMBLE_TRANSMISSION_COUNTER<PREAMBLE_TRANS_MAX:        -   increment PREAMBLE_TRANSMISSION_COUNTER by 1;    -   if PREAMBLE TRANSMISSION COUNTER =PREAMBLE TRANS MAX+1:        -   indicate a Random Access problem to upper layers.            -   based on the back-off parameter in the UE, compute and                apply a back-off value indicating when a new Random                Access transmission shall be attempted;            -   proceed to the selection of a Random Access Resource.

The inventive concepts explained herein may also be described in thefollowing manner.

In certain related art procedures, if a random access response (RAR:RACH MSG 2) is not received within a certain period of time during theRACH procedure, a different back-off time is applied for each mobileterminal and the RACH procedure is attempted again. If there is afailure of the RACH procedure, such is reported to the upper layer (RRCentity). However, this leads to undesirable delays due to the waitingperiod caused by the back-off time.

Thus, instead of waiting to report about any problems that occur in theRACH procedure, if a RACH procedure failure is detected, such failure isreported immediately to the upper layer (RRC entity), then the MACentity (sub-layer) performs error correction and the RACH procedure isperformed again, which results in less delays.

The features described herein can be summarized as follows.

A method of detecting a random access channel (RACH) failure, the methodcomprising: selecting and transmitting a random access channel (RACH)preamble; checking whether a random access response (RAR), whichincludes information about the transmitted RACH preamble, is receivedwithin a specified time; if the RAR is not received within the specifiedtime or if the information about the transmitted RACH preamble includedin the RAR does not match the transmitted RACH preamble, incrementing apreamble transmission counter by 1; comparing a value of the preambletransmission counter and a maximum value of the preamble transmission;indicating to an upper layer that the value of the preamble transmissioncounter is larger than the maximum value of the preamble transmission;and applying a back-off time to delay a subsequent RACH preambletransmission; or if the RAR is received within the specified time and ifthe information about the transmitted RACH preamble included in the RARmatches the transmitted RACH preamble, processing a received uplinkgrant value; if contention resolution is considered unsuccessful,incrementing a preamble transmission counter by 1; comparing a value ofthe preamble transmission counter and a maximum value of the preambletransmission; indicating to an upper layer that the value of thepreamble transmission counter larger than the maximum value of thepreamble transmission; and applying a back-off time to delay asubsequent RACH preamble transmission.

If the contention resolution is unsuccessful, applying a back-off timeand selecting random access resources. The specified time is atransmission time interval (TTI) window. The comparing step comprises:comparing a value of the preamble transit counter that has beenincreased with a preamble transmit max value+1. Before transmitting therandom access preamble, initializing one or more parameters related torandom access is performed. The initialization step involves theinitialization of the transmit counter.

A mobile terminal comprising: a transceiver configured to transmit arandom access preamble; and a processor configured to control thetransceiver and operate such that if a random access response is notreceived within a specified time or if information related to the randomaccess preamble included in the random access response does not matchwith the transmitted random access preamble, incrementing a preambletransmit counter value; comparing a value of the preamble transmitcounter with a preamble transmit maximum value; informing an upper layerthat the preamble transmit counter value is greater than the preambletransmit maximum value; applying a back-off time to delay transmissionof a subsequent random access preamble.

The processor operates such that if a random access response is receivedwithin a specified time and if information related to the random accesspreamble included in the random access response matches with thetransmitted random access preamble, processing an uplink grant valueincluded in the received random access response; incrementing thepreamble transmit counter value by 1, if contention resolution withrespect to the uplink grant value is unsuccessful; comparing a value ofthe preamble transmit counter with a preamble transmit maximum value;and informing the upper layer that the preamble transmit counter valueis greater than the preamble transmit maximum value. The processorapplies the back-off time if contention resolution is unsuccessful. Thespecified time is a transmission time interval (TTI) window.

A method of performing a random access channel (RACH) procedure betweena mobile terminal and a network, the method comprising: detectingwhether a random access response (RAR) is received from the networkwithin a certain time period, the RAR including information about arandom access channel (RACH) preamble transmitted to the network; and ifthe RAR is not received within the certain time period or if theinformation about the transmitted RACH preamble included in the RAR doesnot match the transmitted RACH preamble, performing a first procedure todetect failures in the RACH procedure; and if the RAR is received withinthe certain time period and if the information about the transmittedRACH preamble included in the RAR matches the transmitted RACH preamble,performing a second procedure to detect failures in the RACH procedure.

The first procedure comprises: incrementing a preamble transmissioncounter by 1; comparing a value of the preamble transmission counter anda maximum value of the preamble transmission; indicating to an upperlayer that the value of the preamble transmission counter is larger thanthe maximum value of the preamble transmission; and applying a back-offtime to delay a subsequent RACH preamble transmission.

The second procedure comprises: processing a received uplink grantvalue; and if contention resolution is considered unsuccessful,incrementing a preamble transmission counter by 1; comparing a value ofthe preamble transmission counter and a maximum value of the preambletransmission; indicating to an upper layer that the value of thepreamble transmission counter larger than the maximum value of thepreamble transmission; and applying a back-off time to delay asubsequent RACH preamble transmission. The certain time period isrelated to a transmission time interval (TTI).

The various features and concepts described herein may be implemented insoftware, hardware, or a combination thereof. For example, a computerprogram (that is executed in a computer, a terminal or a network device)for a method and system for detecting failures of random accessprocedures may comprise one or more program code sections for performingvarious tasks. Similarly, a software tool (that is executed in acomputer, a terminal or a network device) for a method and system fordetecting failures of random access procedures may comprise program codeportions for performing various tasks.

The method and system for processing buffer status reports (BSRs)according to the present invention are compatible with various types oftechnologies and standards. Certain concepts described herein arerelated to various types of standards, such as GSM, WCDMA, 3GPP, LTE,IEEE, 4G and the like. However, it can be understood that the aboveexemplary standards are not intended to be limited, as other relatedstandards and technologies would also be applicable to the variousfeatures and concepts described herein.

INDUSTRIAL APPLICABILITY

The features and concepts herein are applicable to and can beimplemented in various types of user devices (e.g., mobile terminals,handsets, wireless communication devices, etc.) and/or network entitiesthat can be configured to support detecting failures of random accessprocedures.

As the various concepts and features described herein may be embodied inseveral forms without departing from the characteristics thereof, itshould also be understood that the above-described embodiments are notlimited by any of the details of the foregoing description, unlessotherwise specified, but rather should be construed broadly within itsscope as defined in the appended claims. Therefore, all changes andmodifications that fall within such scope or equivalents thereof aretherefore intended to be embraced by the appended claims.

1-12. (canceled)
 13. A method of detecting a failure of a random accessprocedure, the method comprising: transmitting, by a mobile terminal, arandom access preamble; monitoring, by a mobile terminal, a firstphysical downlink control channel (PDCCH) to check if a random accessresponse (RAR) including information related to the random accesspreamble matching the transmitted random access preamble is receivedwithin a random access response window, transmitting, by the mobileterminal, uplink data according to the RAR to a base station when theRAR is received; monitoring, by the mobile terminal, a reception of asecond PDCCH to check whether contention resolution is successful untila timer for the contention resolution expires; if the contentionresolution is not successful, incrementing, by the mobile terminal, apreamble transmission counter by 1; if a value of the preambletransmission counter is equal to a maximum value of the preambletransmission+1, indicating, by the mobile terminal, to an upper layerthat there is a problem with the random access procedure; and applying,by the mobile terminal, a back-off time to delay a transmission of asubsequent random access preamble.
 14. The method of claim 13, whereinthe uplink data include a C-RNTI(common-Radio Network TemporaryIdentifier) MAC(medium access control) control element (CE) or aCCCH(common control channel) SDU(service data unit).
 15. The method ofclaim 13, wherein the contention resolution is checked as successful ifthe second PDCCH includes or indicates information associated with theuplink data.
 16. The method of claim 13, wherein the contentionresolution is checked as not successful if a contention resolutionidentity MAC CE included in a MAC PDU(protocol data unit) correspondingto the second PDCCH does not match a CCCH SDU included in thetransmitted uplink data.
 17. The method of claim 13, wherein theindication to an upper layer that there is a problem with the randomaccess procedure is performed before transmitting the subsequent randomaccess preamble.
 18. The method of claim 13, wherein the random accessresponse window is a transmission time interval (TTI) window.
 19. Themethod of claim 13, wherein, before transmitting the random accesspreamble, initializing one or more parameters related to random access.20. The method of claim 19, wherein initializing involves theinitialization of the preamble transmission counter.
 21. A mobileterminal for detecting a failure of a random access procedurecomprising: a transceiver that transmits a random access preamble; and aprocessor that controls the transceiver and monitors a first physicaldownlink control channel (PDCCH) to check if a random access response(RAR) including information related to the random access preamblematching the transmitted random access preamble is received within arandom access response window, transmits uplink data according to theRAR to a base station when the RAR is received; monitors a second PDCCHto check whether contention resolution is successful until a timer forthe contention resolution expires; if the contention resolution is notsuccessful, increments a preamble transmission counter by 1; if a valueof the preamble transmission counter is equal to a maximum value of thepreamble transmission+1, indicates to an upper layer that there is aproblem with the random access procedure; and applies a back-off time todelay a transmission of a subsequent random access preamble.
 22. Themobile terminal of claim 21, wherein the uplink data include aC-RNTI(common-Radio Network Temporary Identifier) MAC(medium accesscontrol) control element (CE) or a CCCH(common control channel)SDU(service data unit).
 23. The mobile terminal of claim 21, wherein thecontention resolution is checked as successful if the second PDCCHincludes or indicates information associated with the uplink data. 24.The mobile terminal of claim 21, wherein the contention resolution ischecked as not successful if a contention resolution identity MAC CEincluded in a MAC PDU(protocol data unit) corresponding to the secondPDCCH does not match a CCCH SDU included in the transmitted uplink data.25. The mobile terminal of claim 21, wherein the indication to an upperlayer that there is a problem with the random access procedure isperformed before transmitting the subsequent random access preamble. 26.The mobile terminal of claim 21, wherein the random access responsewindow is a transmission time interval (TTI) window.
 27. The mobileterminal of claim 21, wherein, before transmitting the random accesspreamble, the processor is configured to initialize one or moreparameters related to random access.
 28. The mobile terminal of claim23, wherein the initialization involves the initialization of thepreamble transmission counter.